| 翻訳と辞書 |
| Requirement prioritization ： ウィキペディア英語版 |
Requirement prioritization
Requirement prioritization is used in Software product management for determining which candidate requirements of a software product should be included in a certain release. Requirements are also prioritized to minimize risk during development so that the most important or high risk requirements are implemented first. Several methods for assessing a prioritization of software requirements exist.〔Lehtola, Laura, Marjo Kauppinen, and Sari Kujala. "(Requirements prioritization challenges in practice )." Product focused software process improvement. Springer Berlin Heidelberg, 2004. 497-508.〕〔Berander, Patrik, and Anneliese Andrews. "(Requirements prioritization )." ''Engineering and managing software requirements.'' Springer Berlin Heidelberg, 2005. 69-94.〕
==Introduction==
In Software product management there exist several sub processes. First of all there is portfolio management where a product development strategy is defined based on information from the market and partner companies. In product roadmapping (or technology roadmapping), themes and core assets of products in the portfolio are identified and roadmap constructions are created. In requirements management candidate software requirements for a product are gathered and organized. Finally, in the release planning activity, these requirements are prioritized and selected for a release, after which the launch of the software product can be prepared. Thus, one of the key steps in release planning is requirements prioritization.
抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』
■ウィキペディアで「Requirement prioritization」の詳細全文を読む
スポンサード リンク
| 翻訳と辞書 : 翻訳のためのインターネットリソース |
Copyright(C) kotoba.ne.jp 1997-2016. All Rights Reserved.
|
|